Received: from mail.webcom.com (mail.webcom.com [206.2.192.68]) by keeper.albany.net (8.7.1/8.7.1) with ESMTP id RAA05211 for <DWARNER@ALBANY.NET>; Wed, 21 Feb 1996 17:55:55 -0500 (EST)
Received: from localhost by mail.webcom.com with SMTP
(1.37.109.15/16.2) id AA210373359; Wed, 21 Feb 1996 14:55:59 -0800
Date: Wed, 21 Feb 1996 14:55:59 -0800
Errors-To: dwarner@ALBANY.NET
Message-Id: <1867.6625T867T1034@mt-inc.com>
Errors-To: dwarner@ALBANY.NET
Reply-To: lightwave@garcia.com
Originator: lightwave@garcia.com
Sender: lightwave@garcia.com
Precedence: bulk
From: johnc@mt-inc.com (John Crookshank)
To: lightwave@mail.webcom.com
Subject: Re: Lightwave 4.0 fp woes
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Status: RO
X-Status:
On 21-Feb-96 07:17:56, Brian Dady (bdady@netcom.com) Emailed:
> On Tue, 20 Feb 1996, John Crookshank wrote:
> How does one
> tell if the OS is aware of the FPU? Sysinfo indicates the presence of
> an FPU, but I would assume it accesses the hardware directly.
If Sysinfo shows an FPU, I don't know of any reason why it wouldn't work,
unless the 68040.library you're using is the improper version. Be sure and
use the version that was suppled with the card, not the version from a
Workbench disk.
> What exactly are the "patch/kludge" files you are referring to? I do
> want to insure that LW4.0 will run on my system before paying for it.
I didn't notice in your previous post that you have a Zuess 68040 card, but
the previous PP&S cards used a "fake" 68040.library, and then did some
strange patching of the OS to get it to work. It is not uncommon for these
manufacturers to sort of "pave their own way" when it comes to designing
their hardware, so the support software ends up being a little
non-standard. PP&S was fairly notorious for this, but it worked fairly
well. I'm not that familiar with the Zuess, but I would strongly suspect
that it needs a proprietary 68040.library supplied by PP&S, and would not
function properly with the standard 68040.library supplied with the OS.